Network management using dynamic recovery and transitioning

ABSTRACT

Preferred embodiments of the invention provide systems and methods to receive a command associated with the network management system, define a work flow based on the command, and execute the work flow on a network element. During execution of the work flow, a network management system determines whether a recovery is necessary and performs a recovery based on a determination that a recovery is necessary.

BACKGROUND INFORMATION

Direct interaction with network elements to change networkconfigurations can result in ad hoc management of a network. Also,attempts to re-configure a network configuration may fail and networkelements may need to be recovered.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the exemplaryembodiments of the disclosure, reference is now made to the appendeddrawings. These drawings should not be construed as limiting, but areintended to be exemplary only.

FIG. 1 illustrates an exemplary implementation of a system according toan embodiment of the disclosure.

FIG. 2 illustrates an exemplary implementation of a network managementsystem according to an embodiment of the disclosure.

FIG. 3 illustrates an exemplary implementation of a web portal accordingto an embodiment of the disclosure.

FIG. 4 illustrates an exemplary screen diagram of a web portal accordingto an embodiment of the disclosure.

FIG. 5 illustrates an exemplary implementation of a web services portalaccording to an embodiment of the disclosure.

FIG. 6 illustrates an exemplary screen diagram of an operations moduleaccording to an embodiment of the disclosure.

FIG. 7 illustrates an exemplary implementation of a method for dynamicwork flow rollback according to an embodiment of the disclosure.

FIG. 8 illustrates an exemplary implementation of a method for dynamicwork flow transitioning according to an embodiment of the disclosure.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A system and process of an exemplary embodiment of the disclosureprovides dynamic work flow rollback and dynamic work flow transitioningwithin a network management system.

FIG. 1 is an exemplary network system according to an embodiment of thedisclosure. System 100 illustrates an exemplary system for supportingtelecommunication networks, such as packet-switched based networksand/or circuit-switched based networks. As illustrated, one or moreinterfaces 103 a-103 n may be coupled to network management system 102and network management system 102 may be coupled to network 101. Thevarious components of system 100 may be further duplicated, combinedand/or integrated to support various applications and platforms.Additional elements may also be implemented in the system to supportvarious applications. Also, while one configuration is shown in FIG. 1,other configurations of these various units may also be implemented. Forexample, the various components of system 100 may be components withinnetwork 101 and network 101 may include one, or any number of theexemplary types of networks operating as a stand alone network or incooperation with each other.

In various exemplary embodiments, network 101 may comprise one or morepacket-switched based networks and/or circuit-switched based networks.As such, network 101 may include, for example, one or more InternetProtocol (IP) networks, wireless communication networks, and/or accessnetworks including, without limitation, dial-up networks, digitalsubscriber line (DSL) networks, broadband wireless access networks,cable modem networks, integrated services digital networks (ISDN),symmetric high-speed digital subscriber line (SHDSL) networks, Ethernetnetworks, metro Ethernet networks, gigabit Ethernet networks, framerelay networks, asynchronous transfer mode (ATM) networks, synchronousoptical networking (SONET) networks operating as a stand alone networkor in cooperation with each other.

Network 101 may be associated with an entity and may provide networkconnectivity to its users (e.g., customers) For example, network 101 maybe associated with a network access provider such as an Internet serviceprovider (ISP) and or any other network access provider that may providenetwork connectivity to enable users (e.g., customers) of the network totransmit information via network 101; a global network provider such asan Internet backbone provider that may provide Internet backboneconnection facilities around the world; a telephone network providerthat may be part of a public switch telephone network; and/or a wirelesscommunication network provider that may provide wireless broadbandand/or mobile phone services to its users (e.g., customers).

Network 101 may be comprised of one or more network elements 104 a-104n. In various exemplary embodiments, network elements 104 a-104 n mayrepresent, for example, addressable, manageable hardware device(s) andassociated software that may perform a telecommunication servicefunction. Network elements 104 a-104 n may include, without limitation:devices associated with level one of the Open Systems Interconnection(OSI) reference model such as add/drop multiplexers, optical add/dropmultiplexers, and/or like devices; devices associated with level two ofthe Open Systems Interconnection (OSI) reference model such as anasynchronous transfer mode (ATM) switch and/or any other like device;devices associated with level three of the Open Systems Interconnection(OSI) reference model such as routers, switches, and or any other likedevices; and/or any other computer networking device that may transmitdata across a network. In various exemplary embodiments, networkelements 104 a-104 n may also represent, for example, automatedtelephone exchanges, digital switches, and/or other like devicesassociated with the public switch telephone network (PSTN).

The entity or entities associated with network 101 may manage network101 via network management system 102. As illustrated in FIG. 1, networkmanagement system 102 may be coupled to network 101 and interfaces 103a-103 n. In various exemplary embodiments, network management system 102may provide a scalable network management application, for example, tomanage devices (e.g., network elements 104 a-104 n) on network 101.Network management system 102 may also provide a web-based interfaceacross Open Systems Interconnection (OSI) layers for network elements104 a-104 n. Network management system 102 may also be coupled to othersystems 105 and provide seamless integration with other systems 105.Other systems may include, for example, provisioning systems,operational support systems (OSS), and fault, configuration, accounting,performance, and security (FCAPS) systems.

Network management system 102 may support various functions associatedwith the management of network 101. For example, network managementsystem 102 may support activation needs for provisioning requests tonetwork elements 104 a-104 n; auto-discovery, reporting, reconciliation,and restoration needs for provisioning platforms; capabilities similarto those of an enterprise management system; and the ability to view ormake changes to virtual devices without accessing the network elementdirectly as described in greater detail below. In various exemplaryembodiments, network management system 102 may be associated with usersthat may use network management system 102 to manage network 101, forexample, and administrators that may configure and/or manage the networkmanagement system. Users may also refer to automated systems associatedwith the network management and/or users of other systems 105 andinterfaces 103 a-103 n. Also, users may be administrators and whether auser may act as an administrator may be dependent upon privilegesassociated with the user as described in greater detail below.

Interfaces 103 a-103 n may represent any number of interfaces associatedwith supporting network management tasks. In various exemplaryembodiments, interfaces 103 a-103 n may be referred to as northboundinterfaces. As such, interfaces 103 a-103 n may send various logicalrequests to network management system 102, which may then transform thelogical requests into native commands to a network element, for example.In an exemplary embodiment, interfaces 103 a-103 n may be associatedwith provisioning systems, operational support systems (OSS), and fault,configuration, accounting, performance, and security (FCAPS) systems.Accordingly, while FIG. 1 illustrates interfaces 103 a-103 n as beingseparate from other systems 105, other configurations may also beimplemented. For example, interfaces 103 a-103 n may be interfaces toother systems 105.

FIG. 2 illustrates a network management system 102 according to variousembodiments of the disclosure. As shown in FIG. 2, network managementsystem 102 may include web portal 201, security management system 202,workflow management system 203, connections module 204, activationmodule 205, and execution module 206.

FIG. 3 illustrates a web portal 201 according to various embodiments ofthe disclosure. As shown in FIG. 3, web portal 201 may include adminportal 301 and web services portal 302. Admin portal 301 may includesecurity module 303, admin module 304 and reports module 305. Web portal201 may provide a single interface to manage all activities associatedwith a network. For example, web portal 201 may provide a graphical userinterface (GUI) that enables a single access point to all networkelements within a network such that users may execute commands on anetwork element, add, delete, or modify network element configurations,troubleshoot and resolve network problems, and/or backup and restoredeleted configurations. Web portal 201 may also provide a graphical userinterface (GUI) that allows an administrator, for example, to add,delete or modify user profiles of users and/or user groups of thenetwork management system, track all actions performed by users of thenetwork management system, send messages to users of the networkmanagement system, run reports based on information contained within thenetwork management system, and/or create credentials and map users thatmay be permitted to access a network element.

In various exemplary embodiments, web portal 201 may be organized basedon tabs. FIG. 4 depicts an exemplary embodiment of a screen diagram 400which illustrates a web portal based on tabs. Screen diagram 400 mayrepresent a graphical user interface (GUI) as described above withrespect to web portal 201. Screen diagram 400 may include a main page401 that may provide a main entry screen from which all modules of thenetwork management system can be accessed. As shown in FIG. 4, screendiagram 400 may also include security tab 402 a, admin tab 403 a,inventory tab 404 a, reports tab 405 a, services tab 406 a, and linkstab 407 a. Each tab may enable users of the network management system toaccess different information and/or services associated with therespective tab. Also, each tab may be associated with different modulesand/or portals of the network management system. For example, securitytab 402 a may be associated with a security module, admin tab 403 a maybe associated with an admin module, inventory tab 404 a may beassociated with an operations portal, reports tab 405 a may beassociated with a reports module, and services tab 406 a may beassociated with a web services portal.

Screen diagram 400 may also include various links on main page 401 thatmay be associated with the respective tabs. For example, main page 401may include a security link 402 b that may be associated with securitytab 402 a, an admin link 403 b that may be associated with admin tab 403a, an inventory link 404 b that may be associated with inventory tab 404a, a reports link 405 b that may be associated with reports tab 405 a,and a services link 406 b that may be associated with services tab 406a. In an exemplary embodiment, if a user of the network managementsystem wishes to navigate to one of the modules and/or portalsassociated with a tab, the user may activate (e.g., click on) the taband/or the link, for example.

Screen diagram 400 may also include other navigational tools such as asite map button 408 and navigation buttons 409, which may enable a userof the network management system to navigate through the web portal oraccess a help page, for example.

Referring back to FIG. 3, in various exemplary embodiments, admin portal301 may include a security module 303 which may allow an administratorto manage users of a network management system. Users of the networkmanagement system may be assigned privileges within the networkmanagement system by way of the roles, groups, and organizations towhich they are associated.

Roles, for example, may be inherited by a user based on a user's groupor organization. Exemplary roles may include, without limitation, systemadmin, admin, user, manager, and complex services user. Each role mayinclude tab permission levels to determine whether or not a user canmodify or view data. The tab permission levels may be associated withvarious tabs of a web portal as shown an described with respect to FIG.4. For example, if a role has view privileges for a tab associated withthe web portal, then the user may only view the data and not modify thedata associated with the tab. Similarly, if a role has modify privilegesfor a tab, a user may modify the data associated with the tab.

User groups and/or organizations may represent a collection of users ofthe network management system that may have a common purpose within anorganization associated with the network. For example, one user groupmay represent all users who share a similar job function. Also, a usergroup may represent all users who have access to a particular networkelement and/or group of network elements. For example, one user groupmay represent all users who have access to the network elementsassociated with a particular network operation center (NOC). User groupsmay also represent all users within a specific geographic region.

In various exemplary embodiments, an administrator may add and/or deleteusers and/or modify information associated with users. For example,security module 303 may include an “add user” tab that may enable anadministrator to add a user and provide information associated with auser to create a user profile. The “add user” tab may include a “userinformation” tab and a “user privileges” tab which may provide aninterface to enter information about a user and the privileges (e.g.,roles and organizations) associated with the user, respectively.Security module 304 may also include a “modify user” tab that may enablean administrator to modify the information associated with users of thenetwork management system. To modify the information associated with auser the “modify user” tab may enable a search for the respective userprovide fields of information that may be modified. Security module 304may also enable the administrator to delete users.

Security module 303 may also include an “audit trail” tab that mayenable an administrator to track security-related actions on a per-userbasis and/or a “command audit” tab that may enable an administrator totrack all commands on a network element. For example, via an “audittrail” tab, an administrator may identify a user and track which networkelements the user accessed. Similarly, via a “command audit” tab, anadministrator may identify a particular network element and track allcommands and/or requests that that may have been executed or arescheduled to be executed on a network element.

Admin portal 301 may also include an admin module 304 which may enablecommunication between and among users of the network management system.For example, admin module 304 may enable administrators to send bannermessages to users of the network management system. In various exemplaryembodiments, admin module 304 may include a “message center” tab thatmay enable an administrator to send a message to one or more users.Using the “message center” tab, an administrator, for example, mayselect individual users (by selecting a specific user identifier) or agroup of users (by selecting a user group) and enter a message to besent to the selected users. Users may also be able to send messages toother users using, for example, the “message center” tab. In doing so,users may be able to send message to other users based on privilegesassociated with the user sending the message.

Admin portal 301 may also include a reports module 305 which may enablereports to be generated that are related to, for example, the activitiesof users within the network management system. For example, reportsmodule may enable “181 Day Reports” to be generated which may display alist of users who have not accessed the network management system in 181days. In various exemplary embodiments, reports module 306 may enablethe generation of other reports that may provide information about, forexample, which network elements a particular user accessed, whatcommands were executed on a particular network element, and/or the like.

FIG. 5 depicts an exemplary embodiment of a web services portal 302according to various embodiments of the disclosure. As shown in FIG. 5,web services portal 302 may include a user module 501 and an adminmodule 502. User module 501 may include an operations module 503, anactivation module 504, and a network elements module 505. Admin module502 may include a policy module 506, a network elements module 507, anda credentials module 508.

Operations module 503 may enable users of the network management systemto execute commands on a network element and/or add, modify and/ordelete network element configurations. Operations module 503 may alsoprovide secure access to network elements to enable users totroubleshoot and resolve network problems.

Operations module 503 may include an “terminal” tab that may enableusers to connect to a network element and enter commands to be executedon the network element. In an exemplary embodiment of the invention, toaccess the network element, operations module may log on to the networkelement in a manner that may be transparent to the user as described ingreater detail below. Also, operations module 503 may batch all commandsentered during a session and then commit the commands to the networkelement at one time, for example.

FIG. 6 depicts an exemplary embodiment of a screen diagram 600 whichillustrates an exemplary “terminal” tab according to various embodimentsof the disclosure. As shown in FIG. 6, screen diagram 600 may include a“terminal” tab 601 which may be accessed by activating (e.g., clickingon) terminal tab button 610. Screen diagram 600 may also include asecurity tab 602 which may be similar to security tab 402 a as describedabove, an admin tab 603 which may be similar to admin tab 403 a asdescribed above, an inventory tab 604 which may be similar to inventorytab 404 a as described above, a reports tab 605 which may be similar tosecurity tab 405 a as described above, a services tab 606 which may besimilar to security tab 406 a as described above, a links tab 607 whichmay be similar to links tab 407 a as described above, a site map button608, navigation buttons 609, connection status portion 611, commandportion 612, and response portion 613.

Using, information about a network element such as a network elementidentifier, protocol type, Internet protocol (IP) address and/or portnumber, a user may search for and locate a device (e.g., networkelement) that the user desires to access. In an exemplary embodiment, auser may only access network elements that the user has privileges toaccess based on the user's role and/or organization. Similarly, a usermay only execute commands that the user has privileges to execute basedon policies that may be associated with the user and/or usercredentials.

Once a user has identified and/or accessed a network element, a user mayinteract with the network element via “terminal” tab 601. As shown inFIG. 6, connection status portion 611 may display the status of theconnection between the network management system and the networkelement. For example, connection status portion 611 may indicate“Connection has been established with [IP Address] (Device Name) on port[Port]”, where [IP address represents an Internet protocol (IP) addressof the network element, “(Device Name) represents a unique identifier ofthe device, and “[Port] represents the port number. Using commandportion 612, a user may enter commands into command field 614. Forexample, a user may enter transaction language one (TL1), common objectrequest broker architecture (CORBA), command line interface (CLI),and/or other like commands into command field 614. In various exemplaryembodiments, different network elements may support different commandsets. In these embodiments, the network management system may validatethe different types of commands and commit the commands to the networkelement as described in greater detail below. Once the commands areentered, the commands may be displayed in response portion 613, forexample. As noted above, operations module 503 may batch all commandsentered during a session and then commit the commands to the networkelement at one time. Users may also activate (e.g., click on) disconnectbutton 615 to disconnect from a network element. Once disconnected,connection status portion 611 may indicate “Not Connected,” for example.

Referring back to FIG. 5, activation module 504 may enable users to add,modify and/or manage scripts for other systems (e.g., other systems 105)that may interface with the network management system. In variousexemplary embodiments, data sent from other systems may be convertedinto, for example, transaction language one (TL1) commands. The scriptsmay represent a set of commands that an other system may apply to anetwork element.

In various exemplary embodiments, a script may include, withoutlimitation, the following three components: a tree structure, avalidation script, and a configuration script. The tree structure mayrepresent the extensible markup language (XML) command structure. Thevalidation script may include a set of commands that may verify whatalready exists in the network element before performing a configurationscript. For example, where a configuration script is associated with across connect, the validation script may validate whether a crossconnect exists before executing a configuration script to establish thecross connect and utilize the ports. The configuration script may add,modify, and/or delete data. For example, a configuration script maycreate a cross connect. Other configuration scripts may define anInternet protocol (IP) interface, create a subnet, and build a bordergateway protocol (BGP) interface to a neighbor router.

Activation module 504 may include an “activation template” tab that mayenable users to add modify and manage template scripts. Template scriptsmay be used repeatedly to perform a particular task associated with aparticular network element. Activation template scripts may beassociated with a particular network element and/or type of networkelement. Also, users may access templates based on privileges of theuser. Using the “activation template” tab, users having requisiteprivileges may add, modify and/or delete template scripts to be executedby themselves and/or other users.

Activation module 504 may also include an “activation request” tab thatmay enable users to select an activation template and execute the scriptassociated with the selected template on a network element. In variousexemplary embodiments, this “activation request” tab may provide analternate to issuing commands using, for example, the “terminal” tab asdescribed above. Also, the “activation request” tab may enable users toschedule scripts to execute at a future date and time. When executing ascript and/or template script, users may enter, for example, networkelement inputs and/or script input inputs that may be inserted intovariable fields in the script. Users may also be able to preview thescript having the inputs inserted into the variable fields beforeexecution.

Network elements module 505 may enable users to add, delete, and/ormodify network element configurations. Network elements module 505 mayinclude an “add element” tab which may include various fields withinwhich users may enter information about a network element. For example,the “add element” tab may include fields associated with a uniqueidentifier, a host name of the network element, a device type to specifythe model name for the network element, a device version to specify therelease version of the network element, an Internet protocol (IP)address, a port number, a credential, a loop back, and or any otherinformation associated with a network element. To add a network element,users may enter the information into the input fields and activate(e.g., click on) an add button associated with the “add element” tab.

To modify or delete a network element, users may search for the networkelement and once located, modify or delete the network element details,for example. A user may add, modify, and/or delete network elementdetails based on the privileges associated with the user.

As noted above, admin module 502 may include a policy module 506. Invarious exemplary embodiments, a policy may refer to a set of commandsthat determine the commands a particular user and/or group of users mayexecute. Policy module 506 may enable administrators, for example, toadd, delete, and/or modify a policy, and/or apply a policy to a group,role, user, or network element.

Admin module 502 may include a “manage policy” tab that may enable anadministrator to manage the policies within the network managementsystem. To create or modify a policy, an administrator may select adevice from a list of devices displayed within the “manage policy” tab.Once selected, an administrator may view, for example, a list ofcommands that are permitted for that network element.

In various exemplary embodiments, a policy may be identified by analphanumeric identifier. To add a policy, an administrator may locate anetwork element and enter an alphanumeric name into, for example a namefield within the “manage policy” tab to associate the network elementwith the name of the policy. Each policy may have an associated defaultpolicy which may determine how the permissions will work. Exemplarydefault policies may include, without limitation, allow, deny, and/orabstain. Allow may represent that, by default, all commands may beallowed, except, for example, those commands that may be explicitlyflagged by add, modify, delete, and/or query permission flags. Deny mayrepresent that, by default, commands may be denied, except, for example,those commands that may be explicitly flagged by add, modify, delete,and/or query permission flags. Abstain may represent that no behaviormay be defined. In an exemplary embodiment, selecting abstain may resultin an implicit deny of any command.

Within the “manage policy” tab, an administrator may associate add,modify, delete, or query permissions to a command. An administrator mayalso apply a policy to groups, users, roles, or network elements. Doingso may define what commands may be executed by certain group(s),user(s), role(s), and on what network elements.

Admin module 502 may also include a network elements module 507 that mayenable an administrator, for example, to return a network element to astate of a previous provisioning in the system. Returning a networkelement to a state of a previous provisioning may provide disasterrecovery for a network element, for example. Network elements module 507may include a “network element reconcile” tab that may enable anadministrator to locate a network element by searching for the networkelement and select any number of commands from a list of commandsprovided with the “network element reconcile” tab and re-execute theselected commands.

Admin module 502 may also include a credentials module 508 that mayenable an administrator to map users and groups to a network element. Invarious exemplary embodiments, each network may be associated with anetwork element ID and a password. As described in greater detail below,the network management system to connect to the network element in amanner that may be transparent to a user. A user may not be able toaccess a network element until the user is mapped to the networkelement.

A credential may be associated with a credential name, a network elementID, and a password of the network element. Credentials module 508 mayinclude a “credential mapping” tab that may enable an administrator toadd a credential. To add a credential, the administrator may inputinformation into, for example, credential name, network element, andnetwork element password fields within the “credential mapping” tab.Once added, an administrator may associate users, user groups, and/ornetwork element groups to the credential. Once a user is associated witha network element, the user may log on to the network element via theweb portal, for example.

Referring back to FIG. 2, security management system 202 may providegeneric security concepts to network management system 102 and network101. For example, security management system 202 may provide credentialscontrol, key escrow services, firewall rules management, access andcontrols specification, secured auditing and/or encryption/decryptionservices. These exemplary generic security concepts may then be utilizedas a base services offering (i.e., a business delegate), to the networkmanagement system to provide a common mechanism for repetitivesecurity-related events such as login credentials control to networkelements.

In various exemplary embodiments, security management system 202 mayalso provide some or all of the data structures and/or algorithmsassociated with performing the functions of security module 303, policymodule 506, network elements module 507, and/or credentials module 508as described above.

Workflow management system 203 may manage work flow (or work unit flow)of the network management system. As described herein, work flow (orwork unit flow) may represent a collection of work units. Generally,work flow may represent any operation performed by the networkmanagement system. For example, work flow may represent operations forconnecting to a network element, communicating with a network, element,and/or interfacing with other systems. Programmatically, a work unit mayrepresent an object that executes in the work flow and returns a stateinformation to the workflow management system.

As noted above, network elements may represent addressable, manageablehardware device(s) and associated software that may perform atelecommunication service function. Each network element may expose oneor more management interfaces that the network management system may useto communicate with and/or manage the network element. The managementinterfaces may use a variety of protocols, depending on the type ofnetwork element. These protocols may include, without limitation, simplenetwork management protocol (SNMP), transaction language one (TL1),command line interface (CLI), extensible markup language (XML), commonobject request broker architecture (CORBA) and/or hypertext transferprotocol (HTTP).

In various exemplary embodiments, network management system 102 mayprovide a single interface to interact with a network element,regardless of the protocol used by the network element. Workflowmanagement system 203 may define a different work unit type for eachprotocol. For example, workflow management system 203 may define asimple network management protocol (SNMP) work unit type, a transactionlanguage one (TL1) work unit type, a command line interface (CLI) workunit type, extensible markup language (XML) work unit type, a commonobject request broker architecture (CORBA) work unit type, a hypertexttransfer protocol (HTTP) work unit type and so forth.

Workflow management system 203 may manage interactions with numerousnetwork elements at a given time. As noted above, to manage work flow,workflow management system 203 may use the state information returned bythe work unit object. Although work unit objects may be defined for eachprotocol, workflow management system 203 may manage work flow usingstate transitions that are based upon patterns. In various exemplaryembodiments, patterns may represent regular expressions that match dataarriving on an incoming stream. Workflow management system may monitorincoming data streams for patterns that may be represented in threeexemplary ways.

First, a good pattern may provide an indication to workflow managementsystem 203 that the one or more operations specified in a command wereperformed successfully and that workflow management system cantransition successfully. Second, a bad pattern may indicate that thetransition was completed, the prompt was found, but an error messageoccurred during the runtime. Such an indication may mean that thetransition is to enter a failure transition, for example. Moreover, whena bad pattern is identified, the workflow management system 203 may waitfor a prompt from the network element. If an error message is receivedfrom the network element, there may be an unknown amount of time beforethe stream may flush to get caught up so the next pattern does not falsehit on stream data. Third, an error pattern may indicate that a problemis found on the stream and the state of the link with the networkelement may no longer be important. If an error pattern is identified,the workflow management system 203 may enter an error state transitionand allow for recovery.

Using the command line interface as an exemplary protocol, as notedabove, workflow management system 203 may define a command lineinterface (CLI) work unit type. The command line interface (CLI) workunit type may be an object-oriented data structure that may definevarious functions for managing work flow. For example, the command lineinterface (CLI) work unit type may define a main execution function maysend a command to a network element and wait for response patterns to bereceived from the network element. The command line interface (CLI) workunit may also define a command that may be sent to a stream andassociated “get” and “set” functions to get and set the command,respectively. In an exemplary embodiment, the “get function may return astring value that is associated with the command.

The command line interface (CLI) work unit may also define good, badand/or error patterns and associated functions for “adding” good, bad,and/or error patterns. Within the definition of the command lineinterface (CLI) work unit, a good pattern may indicate to the commandline interface (CLI) work unit the pattern(s), when found, that mayforce the work flow into a good transition state. In an exemplaryembodiment, a good pattern may indicate that the prompt was found and noerror was generated by the network element. An error pattern mayindicate to the command line interface (CLI) work unit the pattern(s),when found, that may force the work flow into a bad transition state. Inan exemplary embodiment, an error pattern may indicate that a prompt wasfound at the same time an error pattern was found. For example, thenetwork element may return the prompt with a percentage sign (%) toindicate that an error occurred. In this instance, when a prompt isreturned with an error indication (%), the stream returned may the bescrubbed by workflow management system 203 to determine the errorpattern. Scrubbing the stream in this manner may enable workflowmanagement system 203 to understand the stream and make futuretransitions possible. A bad pattern may indicate that total recoveryshould occur. For example, the state of the stream may contain an errorthat requires connection invalidation, recovery, re-login and/orback-out. A bad pattern may be identified by workflow management system203 by directly examining the stream before the prompt is returned.

Other protocol work unit types may be defined and workflow managementsystem 203 may manage work flow using state transitions that are basedupon patterns associated with the respective work unit types.

Connections module 204 provide and manage connections between networkmanagement system 102 and remote facilities such as, e.g., networkelements and/or other systems. As noted above, network management system102 may connect to various network elements using a number of differentprotocols and ports. Connections module 204 may define a model for whichall connections may adhere to and provide a common mechanism forinterfacing with a connection pool manager, for example. In an exemplaryembodiment, the model and mechanism may be defined as an object-orientedclasses or like data structure.

The common model, as defined in connections module 204 may define one ormore methods for enabling connections to remote facilities. For example,connections module 204 may define a method to create a connection and/orhandle to a remote facility and initiate credentials by executing thelogin workflow. In an exemplary embodiment, the creation of a connectionmay be executed as part of the work flow and managed by workflowmanagement system 203. Connections module 204 may also define a methodto close resources in use by a connection and remove a connection to aremote facility.

In various exemplary embodiments, depending on the protocol associatedwith a connection, connections module 204 may define a method to flushany data from a connection so that operations may start over.

Connections module 204 may also define a method that may validate thestability of a connection and return true if the connection id valid, orfalse otherwise. The implementation of this method may vary based on theprotocol that is associated with a connection. Also, in an exemplaryembodiment, method may provide an indication that a communicationvehicle is valid, but not an indication of a logged in state.

Connections module 204 may also define methods to set the state of theconnection, set and/or return the workflow utilized to keep theconnection alive during idle periods, validate that a connection is in a“logged in” stat and that the connection is properly open, return acache utilized in a connection, override a default cache created duringobject creation, store a connection pool manager, return a connectionpool manager for a session, set a session identification for a currentsession, and/or return a stored session identification for the currentsession. In various exemplary embodiments, the session identificationmay be utilized by a connection pool manager to identify a connection.

As noted above, connections module 204 may provide a common mechanismfor interfacing with a connection pool manager. Accordingly, connectionsmodule 204 may define a session manager to manage a connection pool. Invarious exemplary embodiments, the session manager may be defined as anobject-oriented class and/or data structure. The session manager maydefine a function to “get” a connection. In an exemplary embodiment,given a session parameter, the function to “get” a connection may returna new connection from a pool or as a newly created connection. In suchan embodiment, the session parameters may provide session specific datato generate the connection and/or pull a connection from a pool. Thesession manager may also define a “return” connection function that mayreturn the connection back to a pool so that the connection may bereturned back to a connection pool to be used by another thread that mayrequire access to a remote facility. The session manager may defineanother connection that may “remove” a connection that may be determinedto be totally invalid. In an exemplary embodiment, a connection that is“removed” may be completely closed so that it may not be reused.

Activation module 205 may provide a mechanism to implement an activationinterface as described above with respect to activation module 504.

Execution module 206 may provide an interface that enables users ofnetwork management system to interact with network elements and/or otherremote facilities (e.g., other systems 105). As such execution module206 may enable execution of commands to a network element or otherdevice. To do so, execution module 206 may provide a mechanism toreceive one or more commands to be executed and pass the commands to aninterface associated with the device on which the commands are to beexecuted, get a connection from a connection pool, process the list ofcommands based on the interface associated with the device on which thecommands are to be executed, load the commands into work flow units,insert the connection into the work flow, and/or execute the work flow.In various exemplary embodiments, execution module 206 may executecommands based on a priority associated with the user and/or a priorityassociated with the command. For example, a user may be a high-priorityuser (e.g., an operations support user) and network troubleshootingcommands executed by that user may be given a high priority. A user mayalso be a low-priority user (e.g., a provisioning system user) andprovisioning commands executed by that user may be given a lowerpriority. In various exemplary embodiments, the priority of a user maybe assigned dynamically.

In various exemplary embodiments, a network management system using aworkflow management system (e.g., work flow management system 203) andan execution module (e.g., execution module 206), for example, maycooperate to provide recovery during work flow execution. For example,during an attempt to configure the network, if there is a communicationfailure, a connection is lost, an error message occurs, a problem isfound on the stream, and/or any other like failure occurs during workflow execution, work flow execution may enter into a back out state inan attempt to recover from the failure. This recovery during work flowexecution may be referred to herein as “rollback.”

Network management systems according to exemplary embodiments of thedisclosure may support symmetrical and/or asymmetrical rollback.Symmetrical rollback may refer to an instance where a single command maybe recovered by executing a single rollback command. Asymmetricalrollback may refer to an instance where a single command may berecovered by executing multiple commands and/or an instance wheremultiple commands may be recovered by executing a single command.

Prior to execution, work flow may be referred to as “unassigned” workflow. Successful workflow, e.g., work flow that executes without anywork units failing, may be referred to as “complete.” During work flowexecution, if one of the work units associated with a work flow fails,the work flow may enter a back out or recovery state. Upon entering aback out or recovery state, work flow may return to the last back outsync point to allow increment back outs or recoveries. To return to thelast back out sync point, execution in the work flow may be trackedbased on a distinguished state generated by each command. Thedistinguished state may define which command(s) need to be executed forrecovery. For example, a work flow may be associated with three physicalcommands. The network management system may receive a responseindicating a failure of the third command. The work unit may thenassociate itself with a failed state (e.g., a bad pattern). The failedstate of the work unit may trigger a state change of the work flow toback out and/or recover (e.g., the distinguished state). Based on thedistinguished state, the work units associated with the work flow maybehave differently than the intended work flow (e.g., execute commandsto recover).

FIG. 7 depicts flow diagram 700 which illustrates an exemplary methodfor implementing dynamic rollback within a network management system. Inblock 701, a logical command may be received by the network managementsystem. In various exemplary embodiments, the user may interact with aterminal interface (e.g., terminal tab 610) to input a command to beexecuted on a network element and/or an activation interface (e.g.,activation module 504) to execute a script and/or template script thatexecutes one or more commands on a network element. In various exemplaryembodiments, the inputted command and/or the commands executed by thescript may be logical commands associated with the network managementsystem. As such, the logical commands may not be the actual physicalcommands to be executed on the network element.

In block 702, work flow may be defined based on the logical command. Todefine the workflow, a workflow management system (e.g., workflowmanagement system 203) may define a workflow based on the logicalcommand. In various exemplary embodiments, the workflow may include workunits that are based on a configuration file associated with the networkelement on which the command is being executed. For example, a logicalcommand may be a command to build video service. The workflow may bedefined as work units associated with the physical commands to build thevideo service. The configuration file may enable the network managementsystem to determine a script associated with building video service, usethe script to lookup the physical commands for building the videoservice in the configuration file and introduce the physical commandsinto the work flow.

In block 703, the network management system may determine when toexecute the command. In various exemplary embodiments, an executionmodule (e.g., execution module 206) may determine when to execute thecommand based on, for example, a priority associated with the userand/or the command and/or the availability of a connection to thenetwork element.

In block 704, the command may be executed on the network element. Invarious exemplary embodiments, an execution module (e.g., executionmodule 206) may execute the physical command(s) included in the workunits on the network element. To execute the physical command(s) on thenetwork element, the execution module may obtain a direct connection tothe network element from, for example, a connection pool, andcommunicate the physical command(s) to the network element.

In block 705, the network management system may determine whether torollback the command. In various exemplary embodiments, networkmanagement system may determine whether to rollback the command bydetermining whether the a failure occurred. For example, the networkmanagement system may determine whether a communication failureoccurred, a connection was lost, an error message occurred, a problemwas found on the stream, a user forced a back out by executing apreemptive request to cause a recovery, test command are to berecovered, and/or any other like failure occurred during work flowexecution.

In block 706, recovery (or rollback) may be performed. As noted above,execution in the work flow may be tracked based on a distinguished stategenerated by each command. The distinguished state may define whichcommand(s) need to be executed for recovery. To perform the recovery,the network management system may execute those command(s) needed forrecovery on the network element.

In block 707, work flow may continue based on a determination that thecommand does not require recovery.

In various exemplary embodiments, the network management system using aworkflow management system (e.g., work flow management system 203) andan execution module (e.g., execution module 206), for example, maycooperate to provide dynamic transitioning during work flow execution. Anetwork management system according to various embodiments of thedisclosure may support static and/or dynamic work unit definitions. Astatic work unit definition, as referred to herein, may be a work unitdefinition that is fixed (e.g., predefined). A dynamic work unitdefinition, as referred to herein, may be a work unit definition thatcan interrogate and determine the state of the work flow and changestate based on the determination.

FIG. 8 depicts flow diagram 800 which illustrates an exemplary methodfor implementing dynamic rollback within a network management systemwith blocks 801 802 operating as described above for blocks 701 and 702,respectively. Also, in block 802, when defining the work flow, a trapmay be specified upon a certain condition. A trap may refer aprogramming code or signal that may be designed to capture errors andreveal where the errors are. A trap may also refer to aprocessor-generated exception. For example, a trap may be specified forwhen a network element fails and enters into a known state such as acommunication failure.

In block 803, the network management system may determine whether thecondition has been met. For example, while executing work flow, thenetwork management system may monitor transition states of work unitsand based on the transition states, determine whether the condition hasbeen met. Using the example described above, the network management maydetermine that the network element failed and entered into acommunication failure.

In block 804, a work unit may be called on the trap. For example, whenthe network element enters into a communication failure, a call may bemade to a work unit to re-establish communication with the networkelement.

In block 805, the work unit may execute a call back to the workflow. Forexample, the work unit may place a call back establishing communicationwith the network element.

In block 806, work flow may continue.

In various exemplary embodiments, other forms of dynamic transitioningmay be supported by a network management system. For example, a networkmanagement system may support delayed transitions by placing timers ontransitions. In these embodiments, if a failure occurs during work flow,timers may be specified in the work flow to determine when a retry mayoccur. Network management systems may also support pluggable,customizable transitions. In these embodiments, actions may be definedfor when a particular state happens on a device. For example, when awork unit executes, the work unit may trigger another work unit toexecute (e.g., when the state of the work unit triggers another workunit).

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

1. A method, comprising: receiving a command associated with a networkmanagement system; defining a work flow based on the command; executingthe work flow on a network element; determining whether a recovery isnecessary; and performing a recovery based on a determination that arecovery is necessary.
 2. The method according to claim 1, furthercomprising: determining when to execute the work flow.
 3. The methodaccording to claim 2, wherein the determination of when to execute thework flow is based on a priority of a user attempting to execute thecommand or the availability of a connection to the network element. 4.The method according to claim 1, wherein the work flow includes one ormore work units that are based on a configuration file associated withthe network element.
 5. The method according to claim 4, furthercomprising: converting the command associated with the networkmanagement system into a command associated with the network elementusing the configuration file.
 6. The method according to claim 5,wherein the one or more work units include the command associated withthe network element.
 7. The method according to claim 1, wherein arecovery is necessary if a failure associated with the network elementoccurs.
 8. The method according to claim 1, further comprising: definingone or more predetermined commands associated with recovery of thecommand; and performing the recovery using the one or more predeterminedcommands.
 9. A method, comprising: receiving a command associated with anetwork management system; defining a work flow based on the command;executing the work flow on a network element; determining whether acondition has been met; calling a work unit associated with an exceptionbased on a determination that the condition has been met; and executingthe work unit associated with the exception.
 10. The method according toclaim 9, wherein the work flow includes one or more work units that arebased on a configuration file associated with the network element. 11.The method according to claim 10, further comprising: converting thecommand associated with the network management system into a commandassociated with the network element using the configuration file. 12.The method according to claim 11, wherein the one or more work unitsinclude the command associated with the network element.
 13. A system,comprising: a network management system to receive a command associatedwith the network management system and define a work flow based on thecommand; and an execution module to execute the work flow on a networkelement, wherein during execution of the work flow, the networkmanagement system determines whether a recovery is necessary andperforms a recovery based on a determination that a recovery isnecessary.
 14. The system according to claim 13, wherein the networkmanagement system determines when to execute the work flow.
 15. Thesystem according to claim 14, wherein the determination of when toexecute the work flow is based on a priority of a user attempting toexecute the command or the availability of a connection to the networkelement.
 16. The system according to claim 13, wherein the work flowincludes one or more work units that are based on a configuration fileassociated with the network element.
 17. The system according to claim16, wherein the network management system converts the commandassociated with the network management system into a command associatedwith the network element using the configuration file.
 18. The systemaccording to claim 17, wherein the one or more work units include thecommand associated with the network element.
 19. The system according toclaim 13, wherein a recovery is necessary if a failure associated withthe network element occurs.
 20. The system according to claim 13,wherein the network management system defines one or more predeterminedcommands associated with recovery of the command and performs therecovery using the one or more predetermined commands.
 21. The systemaccording to claim 13, wherein the network management system comprisescomputer readable code stored in an electronic storage medium adapted tocause a processor to receive a command associated with the networkmanagement, define a work flow based on the command, determine whether arecovery is necessary and perform a recovery based on a determinationthat a recovery is necessary.
 22. The system according to claim 13,wherein the execution module comprises computer readable code stored inan electronic storage medium adapted to cause a processor to execute thework flow on a network element.
 23. A system, comprising: a networkmanagement system to receive a command associated with a networkmanagement system and define a work flow based on the command; and anexecution module to execute the work flow on a network element, wherein,during execution of the work flow, the network management systemdetermines whether a condition has been met, calls a work unitassociated with an exception based on a determination that the conditionhas been met, and wherein the execution module executes the work unitassociated with the exception.
 24. The system according to claim 23,wherein the work flow includes one or more work units that are based ona configuration file associated with the network element.
 25. The systemaccording to claim 24, wherein the network management system convertsthe command associated with the network management system into a commandassociated with the network element using the configuration file. 26.The system according to claim 25, wherein the one or more work unitsinclude the command associated with the network element.
 27. The systemaccording to claim 23, wherein the network management system comprisescomputer readable code stored in an electronic storage medium adapted tocause a processor to receive a command associated with the networkmanagement, define a work flow based on the command, determine whether acondition has been met and call a work unit associated with an exceptionbased on a determination that the condition has been met.
 28. The systemaccording to claim 23, wherein the execution module comprises computerreadable code stored in an electronic storage medium adapted to cause aprocessor to execute the work flow on a network element and execute thework unit associated with the exception.